Ports Used By Local Edition

Local Edition has two types of ports:

• Public ports on which services are exposed outside of the cluster. They are applicable to Load Balancer (LB) services.

• Cluster-only ports are defined for services of type ClusterIP. They are used for inter-component networking. You can change the service type using Helm values.

You can also configure LB services as ClusterIP and expose them using ingress controllers. Some ports are not bound to any service but are exposed by individual pods. These ports are used by liveness and readiness probes to check and maintain pods' availability.

logcollector-svc (in v6.2.0)

Ports	Scope	Notes
24224	ClusterIP	HTTP port for forwarded input.
8080	ClusterIP	LogSync HTTP API endpoint allows other components to trigger LogSync operations via HTTP requests.

logcollector-pod (in v6.2.0)

Ports	Scope	Notes
8080	Container	HTTP port used by liveness and readiness probes.

cache-svc (in v6.0.0+)

Ports	Scope	Notes
8080	ClusterIP	HTTP port for cache clients using the REST protocol.
10080	ClusterIP	Ignite thin clients that need to connect to an Ignite pod directly.

cache-deploy (in v6.0.0+)

Ports	Scope	Notes
47100	ClusterIP	Port for members of the Ignite ring to communicate via gossip protocol.
47500	ClusterIP	Port for members of the Ignite ring to discover each other and maintain the ring.
49112		JMX port
10800		Maps to cache-svc:10080
8080		Maps to cache-svc:8080

loader-svc (cachloader-svc in v6.0.0; loader-svc from v6.1.0+)

Ports	Scope	Notes
8082	ClusterIP	HTTP and generic TCP port for k8s cron jobs - loader-delta, loader-full, and startup-loader to invoke data loading into cache.

loader-deploy (cacheloader-deploy in v6.0.0; loader-deploy from v6.1.0+)

Ports	Scope	Notes
8082		HTTP port bound to cacheloader-svc:8082. This same probe is used by the loader's (cacheLoader in v6.0.0; loader from v6.1.0+) startup, liveness, and readiness probes.

configui-svc (in v6.0.0+)

Ports	Scope	Notes
80	LB	HTTP port that redirects to the pod's 8080 port.
443	LB	HTTPS port that redirects to the pods' 8443 port. It is needed only if HTTPS is enabled for ConfigUI.

configui-deploy (in v6.0.0+)

Ports	Scope	Notes
8080		configui-svc:80
8443		configui-svc:443
8082	Container	HTTP port used by liveness and readiness probes.

platformapi-svc (in v6.0.0+)

Ports	Scope	Notes
7080	LB	HTTP port for allowing access to Platform API. Depending on your needs, you can make this ClusterIP using Values.global.k8sServiceType.
7443	LB	HTTP port for allowing access to Platform API. Depending on your needs, you can make this ClusterIP using Values.global.k8sServiceType.

platformapi-deploy (in v6.0.0+)

Ports	Scope	Notes
7080
7443		Maps to platformapi-svc:7443
8082	Container	HTTP port used by liveness and readiness probes.

trafficmanager-svc (in v6.0.0+)

Ports	Scope	Notes
80	LB	HTTP port for traffic calls. Depending on your needs, you can make this ClusterIP using Values.global.k8sServiceType.
443	LB	HTTP port for traffic calls. Depending on your needs, you can make this ClusterIP using Values.global.k8sServiceType.
1443	LB	HTTPS with mTLS port for traffic calls. Depending on your needs, you can make this ClusterIP using Values.global.k8sServiceType.

trafficmanager-deploy (in v6.0.0+)

Ports	Scope	Notes
20080		Maps to trafficmanager-svc:80. Depending on your needs, you can make this ClusterIP using Values.global.k8sServiceType.
20443		Maps to trafficmanager-svc:443. Depending on your needs, you can make this ClusterIP using Values.global.k8sServiceType.
1443		Maps to trafficmanager-svc:1443. Depending on your needs, you can make this ClusterIP using Values.global.k8sServiceType.
8082	Container	Port used by startup liveness and readiness probes.

trafficmanager-deploy/fluent-bit (in v6.0.0+)

Ports	Scope	Notes
24320	Container	Verbose Logging: When enabled, the traffic manager writes request metadata to this port using the fluent-bit FORWARD protocol.
24321	Container	Verbose Logging: When enabled, the traffic manager writes inbound request headers and payload to this port using the fluent-bit FORWARD protocol.
24322	Container	Verbose Logging: When enabled, the traffic manager writes target request headers and payload to this port using the fluent-bit FORWARD protocol.
24323	Container	Verbose Logging: When enabled, the traffic manager writes target response headers and payload to this port using the fluent-bit FORWARD protocol.
24324	Container	Verbose Logging: When enabled, the traffic manager writes outbound response headers and payload to this port using the fluent-bit FORWARD protocol.

fluent-bit common (in v6.0.0+)

Ports	Scope	Notes
2020	Container	Port used by fluent-bits liveness and readiness probes.